Thank you for you reply. After your first reply I suspected that this crash log from jailbroken device, because there is strange library /Library/MobileSubstrate/DynamicLibraries/OTRLocation.dylib, so I googled this lib and found some info related with jailbreaking. We do not have ios devices with ios 13.5.1 to check, but on ios simulator app works well. Thanks.

As i can see there was exception in obj-c block that was not caught by you code, so gdc has caught it and scheduled std::terminate() call

Unfortunately, yes, if you want to continue to develop apps you have to upgrade your hardware. We faced the same problem, so we upgraded our hardware. It is Apple's politic.

When upload crash file i receive this message: "An error occured while uploading this log. Please try again later." So I share it via dropbox: [https://www.dropbox.com/s/bh89nm7n0l5a65g/2023-08-03_00-26-07.0838_%2B0700-3bd4b0ba90930b44b6ec68258592ceb79b554d46.crash?dl=0]

I have one, have no idea what can cause it in my program Thread 0 name: Thread 0 Crashed: 0 WebCore 0x000000019242be5c WTF::Detail::CallableWrapper<WebCore::VideoFullscreenInterfaceAVKit::doExitFullscreen()::$_9, void>::call() + 44 (VideoFullscreenInterfaceAVKit.mm:1557) 1 JavaScriptCore 0x000000018bc1c650 WTF::RunLoop::performWork() + 200 (Function.h:82) 2 JavaScriptCore 0x000000018bc1d3ec WTF::RunLoop::performWork(void*) + 36 (RunLoopCF.cpp:46) 3 CoreFoundation 0x0000000180a24414 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 28 (CFRunLoop.c:1972) 4 CoreFoundation 0x0000000180a351a0 __CFRunLoopDoSource0 + 208 (CFRunLoop.c:2016) 5 CoreFoundation 0x000000018096e6f8 __CFRunLoopDoSources0 + 368 (CFRunLoop.c:2061) 6 CoreFoundation 0x000000018097405c __CFRunLoopRun + 828 (CFRunLoop.c:2951) 7 CoreFoundation 0x0000000180987bc8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268) 8 GraphicsServices 0x000000019caf7374 GSEventRunModal + 164 (GSEvent.c:2200) 9 UIKitCore 0x00000001832fdb58 -[UIApplication _run] + 1100 (UIApplication.m:3511) 10 UIKitCore 0x000000018307f098 UIApplicationMain + 364 (UIApplication.m:5064) 11 XXXXXXXXX 0x00000001028c727c main + 108 (main.m:24) 12 dyld 0x00000001042c5da4 start + 520 (dyldMain.cpp:879)

I also recomed you to buy m1-macbook or m1-macmini, as for me m1-macmini is the perfect decision(with at least 16gb ram and 512 gb ssd), intel-macbook is the past epoch, Apple will not support intel-macbooks in a few years.

It works after 10 min of inactivity, maybe some problems with bluetooth. I had to turn off then turn on bluetooth to link them, without this manipulation they don't want to link.

You can restore your iphone to ios15.7 by downloading ios15.7 firmware and restore from Finder. Before doing it backup your iphone. Download firmware from here https://ipsw.me/

Can check it

First of all app should read receipt data, validate it by Apple certificate, decode data to get purchases and another info to configure/lock/unlock some functionality, by getting receipt data during debug your app will be promted to enter login and pwd of sandbox account. You should try to purchase with sandbox account.

Try to find out crashlog in Privacy & Security -> Analytics & Improvements-> Analytics Data with name pattern "YourAppName-date of crash-time of crash.ips"(also maybe *.ips.synced)

Так пусть определенный круг скинется и будет тебе аккаунт с сертификатом для подписи.

Did reviewers provide some crash-report to research?

no :(

Hi, every relaunch/rebuild reinstalls app with new generated guid in the intall path of the app, that's why app can not find the file in app documents directory.